When relating a deferred index type over a mapped type on the source side ... - #56742
Conversation
…side, actually compare against the mapped type's apparent keys
|
TypeScript Bot (@typescript-bot) test this |
|
Heya Wesley Wigham (@weswigham), I've started to run the regular perf test suite on this PR at b6e3704. You can monitor the build here. |
|
Heya Wesley Wigham (@weswigham), I've started to run the diff-based top-repos suite on this PR at b6e3704. You can monitor the build here. Update: The results are in! |
|
Heya Wesley Wigham (@weswigham), I've started to run the parallelized Definitely Typed test suite on this PR at b6e3704. You can monitor the build here. Update: The results are in! |
|
Heya Wesley Wigham (@weswigham), I've started to run the tarball bundle task on this PR at b6e3704. You can monitor the build here. |
|
Hey Wesley Wigham (@weswigham), I've packed this into an installable tgz. You can install it for testing by referencing it in your and then running There is also a playground for this build and an npm module you can use via |
|
Hey Wesley Wigham (@weswigham), the results of running the DT tests are ready. |
|
Wesley Wigham (@weswigham) Here are the results of running the top-repos suite comparing Everything looks good! |
|
TypeScript Bot (@typescript-bot) perf test this |
|
Heya Jake Bailey (@jakebailey), I've started to run the regular perf test suite on this PR at 682b7d3. You can monitor the build here. Update: The results are in! |
|
Jake Bailey (@jakebailey) Here they are:
CompilerComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
tsserverComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
StartupComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
actually compare against the mapped type's apparent keys.
FIxes #56718 - the emit is fine (all the anonymous/local types are inlined and duplicated like you'd expect), our relationship logic was just too strict when relating deferred index types of mapped types, so in the emit, when the
keyof {big anonymous mapped type}got duplicated into two places, we failed to recognize them as the same type.